Man page: Add reference to cargo-build page

diff --git a/src/etc/cargo.1 b/src/etc/cargo.1
index 300ccd17eff9ec4004ef6080609bd92b8ad4dbc2..a9a598bf06fd6e907217e6a3356a2c0f5d9ac266 100644 (file)
--- a/src/etc/cargo.1
+++ b/src/etc/cargo.1
@@ -34,105 +34,57 @@ Configure coloring of output
 
 To get extended information about commands, run 'cargo help <command>'
 
-.SS build
-Compile the current project
-.TP
-\fB\-h, \-\-help\fR
-Print this message
-.TP
-\fB\-p\fR \fISPEC\fR, \fB\-\-package\fR \fISPEC ...\fR
-Package to build
-.TP
-\fB\-j\fR \fIN\fR, \fB\-\-jobs\fR \fIN\fR
-The number of jobs to run in parallel
-.TP
-\fB\-\-lib\fR
-Build only this package's library
-.TP
-\fB\-\-bin\fR \fINAME\fR
-Build only the specified binary
-.TP
-\fB\-\-example\fR \fINAME\fR
-Build only the specified example
-.TP
-\fB\-\-test\fR \fINAME\fR
-Build only the specified test target
-.TP
-\fB\-\-bench\fR \fINAME\fR
-Build only the specified benchmark target
 .TP
-\fB\-\-release\fR
-Build artifacts in release mode, with optimizations
-.TP
-\fB\-\-features\fR \fIFEATURES\fR
-Space-separated list of features to also build
-.TP
-\fB\-\-no-default-features\fR
-Do not build the `default` feature
-.TP
-\fB\-\-target\fR \fITRIPLE\fR
-Build for the target triple
-.TP
-\fB\-\-manifest-path\fR \fIPATH\fR
-Path to the manifest to compile
-.TP
-\fB\-v, \-\-verbose\fR
-Use verbose output
-.TP
-\fB\-q, \-\-quiet\fR
-No output printed to stdout
+\fBcargo-build\fR(1)
+Compile the current project
 .TP
-\fB\-\-color\fR \fIWHEN\fR
-Coloring: auto, always, never
-
-.PP
-If the \fB--package\fR argument is given, then \fISPEC\fR is a package id
-specification which indicates which package should be built. If it is not given,
-then the current package is built. For more information on \fISPEC\fR and its
-format, see the `cargo help pkgid` command.
-
-Compilation can be configured via the use of profiles which are configured in
-the manifest. The default profile for this command is `dev`, but passing the
-\fB--release\fR flag will use the `release` profile instead.
-
-
-
-.SS clean
+\fBcargo clean\fR
 Remove the target directory with build output
-.SS doc
+.TP
+\fBcargo doc\fR
 Build this project's and its dependencies' documentation
-.SS init
+.TP
+\fBcargo init\fR
 Create a new cargo project in the current directory
-.SS install
+.TP
+\fBcargo install\fR
 Install a Rust binary
-.SS new
+.TP
+\fBcargo new\fR
 Create a new cargo project
-.SS run
+.TP
+\fBcargo run\fR
 Build and execute src/main.rs
-.SS test
+.TP
+\fBcargo test\fR
 Run the tests for the package
-.SS bench
+.TP
+\fBcargo bench\fR
 Run the benchmarks for the package
-.SS update
+.TP
+\fBcargo update\fR
 Update dependencies in Cargo.lock
-.SS package
+.TP
+\fBcargo package\fR
 Generate a source tarball for the current package
-.SS publish
+.TP
+\fBcargo publish\fR
 Package and upload this project to the registry
-.SS uninstall
+.TP
+\fBcargo uninstall\fR
 Remove a Rust binary
-.SS search
+.TP
+\fBcargo search\fR
 Search registry for crates
-.SS version
+.TP
+\fBcargo version\fR
 Print cargo's version and exit
 
 .SH FILES
 
 .TP
 ~/.cargo
-Directory in which Cargo stores repository data. Cargo can be instructed to use
-a .cargo subdirectory in a different location by setting the CARGO_HOME
-environment variable.
+Directory in which Cargo stores repository data. Cargo can be instructed to use a .cargo subdirectory in a different location by setting the CARGO_HOME environment variable.
 
 .SH "EXAMPLES"
 Build a local package and all of its dependencies